This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
~Kirk Cisponegenetsi 4.Jun.03 11:59 AM a Web browser Applications DevelopmentAll ReleasesAll Platforms
Hi,
I have reviewed all the options that are currently available to me to export a Notes Document in XML (DXL) format. Here is a table of what I found:
Notes R5 - LotusScript
----------------------
the only way to Export data is to use Paul Ray's DXLSX.DLL wrapper. This works perfectly and the DXL contains everything that is in the original document.
Con: only runs on Win32 platform (DXLTools.DLL is Win32).
Notes R5 - Java
---------------
Here I can use the generateXML function to get the "simple" items. To get the other items (for eg. RichTextItem) I need to use parseXML on that Item. I then need to add these nodes to the origional DXL document.
Con: seems overly complex to me. I also need to add extra XML directives to be able to reimport the data that I exported!
Notes R6 - LotusScript
----------------------
Here the support seems perfect (to me anyway).
Notes R6 - Java
---------------
Same support as with R5! Where are the NotesDXLExporter (DXLExporter) classes so that I could export a document?
Con: same as R5
So here is my problem:
We have a back-end tool that allows us to archive a file. We currently export data from Notes via LotusScript (R6) and then use native Win32 calls to archive the DXL file.
I would now like to make this cross-platform. We already have the Java Classes to archive a file. I would now like to be able to create a DXL file in Java - but there is no DXLExporter class!
So how do I export a document in DXL format from Notes using Java?
Any ideas or have I missed the boat somewhere?
Thanx for any help given
Ursus
PS: I have thought of using LS as the controlling entity. I could encapsulate my calls to Java in a script lib and LS would not really know that the archiving is being done via Java. I could then create the DXL via LS. This seems a bit "messy" to me ;o) The only bit of the puzzel that I am missing is being able to export the entire document in DXL via Java.